270 enforce line endings#271
Merged
Merged
Conversation
Closed
Collaborator
Author
|
Same was done here |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
krowvin
force-pushed
the
270-enforce-line-endings
branch
from
e5eb908 to
010465d
Compare
|
Collaborator
Author
|
The CI integration tests were cancelled, they're missing that "/" too However, the PR'd changes are strictly for file EOL |
Enovotny
approved these changes
Mar 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The .editorconfig will make it so the files save with specific EOL chars
the .gitattributes will make it so the files commit with specific EOL chars
This will happen for the entire repo.
I also ran
git ls-files --eolto try and see if any files needed this applied and they all look to be in order!